Hi guys, any update on this ?

Actually yes, there was this question above: The key passed to Seek is a byte slice, but all other keys passed to the goka.Iterator are strings. Can the key passed to Seek be a string?

As far as I remember, storage.Iterator uses byte slices too. So there it isn't a problem.

Sure ;)

iterator.Seek([]byte("this is my key"))

;)

What I meant is that the whole interface of goka.Iterator is defined with keys as strings. So Seek() should take a string, like this:

type Iterator interface {
	Next() bool
	Key() string
	Value() (interface{}, error)
	Release()
	Seek(key string) bool
}

Similarly, creating the iterator would ideally be done with strings:

func (f *file) IteratorWithRange(start, limit string) (Iterator, error) {

Is there any issue with that?

;) I see... In fact I added like that so that it's complient with the interface of the leveldb library.
https://github.com/syndtr/goleveldb/blob/master/leveldb/iterator/iter.go

I guessed so. The storage.Iterator is defined with keys as byte slices because LevelDB uses byte slices.

Still, since we work with string keys at the goka package level, I think it would make sense to keep string keys there. Or change all keys to byte slices, but that would break way too many things.

ok get it.. I update the code

Excellent! And this one should take strings too: func (v *View) IteratorWithRange(start, limit []byte) (Iterator, error) {

Besides these []byte thing, the PR looks pretty good to me. Thanks for contributing.